Good afternoon,
I have a DOORS question, I created a partition and tested it in another DOORS database to make sure everything was ok, all the modules in the partition are read only, why can't I delete the partition from the database I tested it on?
Also, I know you can create Project Archive, however why is that option dimmed on my database?
DXLUser - Fri Sep 09 12:47:09 EDT 2011 |
|
Re: DOORS Question llandale - Fri Sep 09 14:29:00 EDT 2011
Sorry I forgot the correct verbs associated with Partitions.
You need to remember that there is [1] a Partition 'Definition' which is like a 'Plan', and then there is [2] an Actual Partition. You create a 'Definition' in the Home database, then create a 'Partition' and send it to the Away, which eventually sends it back where the home 'Recovers' it. Lets define which tools I'm going to lend my friend (the Definition), then put them in a tool box and loan loan them.
You need to 'Recover' the partition in the Home database before you can 'delete' that partition definition. There are two 'recover' methods, [1] where the Away database sends it back and you update the Home with changes made at the Away, or [2] 'cancel' which divorces you from the Away version. If you Cancel at home you should Cancel at the Away or folks will get confused.
|
|
Re: DOORS Question DXLUser - Fri Sep 09 15:24:02 EDT 2011 llandale - Fri Sep 09 14:29:00 EDT 2011
Sorry I forgot the correct verbs associated with Partitions.
You need to remember that there is [1] a Partition 'Definition' which is like a 'Plan', and then there is [2] an Actual Partition. You create a 'Definition' in the Home database, then create a 'Partition' and send it to the Away, which eventually sends it back where the home 'Recovers' it. Lets define which tools I'm going to lend my friend (the Definition), then put them in a tool box and loan loan them.
You need to 'Recover' the partition in the Home database before you can 'delete' that partition definition. There are two 'recover' methods, [1] where the Away database sends it back and you update the Home with changes made at the Away, or [2] 'cancel' which divorces you from the Away version. If you Cancel at home you should Cancel at the Away or folks will get confused.
Hi,
Sorry this is the first time I deal with partitions, you said I have an option to "cancel" How would I do that because I don't see that option?
|
|
Re: DOORS Question llandale - Sat Sep 10 20:00:49 EDT 2011 DXLUser - Fri Sep 09 15:24:02 EDT 2011
Hi,
Sorry this is the first time I deal with partitions, you said I have an option to "cancel" How would I do that because I don't see that option?
See "Recover" instead of "Cancel". Sorry, not so good at remembering those verbs.
To answer your original question, if you are done 'testing' you can "Return" the partition from the Away database and delete that Return file, and then "Recover" the partition in the Home, and you are back to the starting point. However, it seems to me you would want to practice "Return" at Away and then "Rejoin" at Home to complete your testing.
The Partition section in the DOORS User manual is actually pretty good and you should read it, play around a little, then read it again. Having a 2nd temp database will help a lot.
"Create Definition" is just playing around in the Home database getting read to make a partion. It defines which data goes and the access rights the Away folks will have.
"Remove Definition" is when the Home folks don't need that defintion anymore.
"Export Partition" is making a file for import into the Away database, and locks down any data in the Home that is editable in the Away.
"Import Partition" is loading the Partition in the Away database
"Synchronize" is when the Away folks have been editing but are not done, the Home folks can see the progress to date. Both the Away and the Home folks use the same verb; so lets pretend you "Synchronize Send" and "Synchronize Accept".
"Return" is when the Away folks are done editing and send the partition data back Home.
"Rejoin" is when the Home folks accept the Returned partition.
"Recover" is when the Home folks change their minds and don't want the Partition to come back. The Away folks should be advised so they can "Return" the partion, then delete the return files.
Now if you just want some Away folks to SEE your Home data but not edit any of it, you can create a read Definition, Export it, immediately Recover it, and the Away folks Import it. The Away folks could immediately Return it (with no home Rejoin), but they could also leave it as-is to remind them it's Home data.
Keeping in mind I've only played a little with partitions, I infer the following realities:
>> You cannot 'Remove' a Home definition while the Partion is Exported.
>> You cannot 'Remove' an Away Imported definition at all. This definition goes when you 'Return'.
>> If you were to Archive a project with an active Parition, I can see no way to coordinate such a Restored project with the Partition. That is, the restored project will not have that partition. Its thus possible that the DOORS folks deciced to disallow archiving of such Projects.
>> I imagine some difficulties if a module was in 2 partitions, even if its editable only in one.
>> I imagine some difficulties of putting a module you have Imported into an Exported Partion.
>> I imagine there are awkward scenarios the DOORS folks did not consider that will mess up your partitions very seriously.
You should architect your partitions mindfully and carefully and avoid any overlap.
|
|
Re: DOORS Question DXLUser - Mon Sep 12 10:22:33 EDT 2011 llandale - Sat Sep 10 20:00:49 EDT 2011
See "Recover" instead of "Cancel". Sorry, not so good at remembering those verbs.
To answer your original question, if you are done 'testing' you can "Return" the partition from the Away database and delete that Return file, and then "Recover" the partition in the Home, and you are back to the starting point. However, it seems to me you would want to practice "Return" at Away and then "Rejoin" at Home to complete your testing.
The Partition section in the DOORS User manual is actually pretty good and you should read it, play around a little, then read it again. Having a 2nd temp database will help a lot.
"Create Definition" is just playing around in the Home database getting read to make a partion. It defines which data goes and the access rights the Away folks will have.
"Remove Definition" is when the Home folks don't need that defintion anymore.
"Export Partition" is making a file for import into the Away database, and locks down any data in the Home that is editable in the Away.
"Import Partition" is loading the Partition in the Away database
"Synchronize" is when the Away folks have been editing but are not done, the Home folks can see the progress to date. Both the Away and the Home folks use the same verb; so lets pretend you "Synchronize Send" and "Synchronize Accept".
"Return" is when the Away folks are done editing and send the partition data back Home.
"Rejoin" is when the Home folks accept the Returned partition.
"Recover" is when the Home folks change their minds and don't want the Partition to come back. The Away folks should be advised so they can "Return" the partion, then delete the return files.
Now if you just want some Away folks to SEE your Home data but not edit any of it, you can create a read Definition, Export it, immediately Recover it, and the Away folks Import it. The Away folks could immediately Return it (with no home Rejoin), but they could also leave it as-is to remind them it's Home data.
Keeping in mind I've only played a little with partitions, I infer the following realities:
>> You cannot 'Remove' a Home definition while the Partion is Exported.
>> You cannot 'Remove' an Away Imported definition at all. This definition goes when you 'Return'.
>> If you were to Archive a project with an active Parition, I can see no way to coordinate such a Restored project with the Partition. That is, the restored project will not have that partition. Its thus possible that the DOORS folks deciced to disallow archiving of such Projects.
>> I imagine some difficulties if a module was in 2 partitions, even if its editable only in one.
>> I imagine some difficulties of putting a module you have Imported into an Exported Partion.
>> I imagine there are awkward scenarios the DOORS folks did not consider that will mess up your partitions very seriously.
You should architect your partitions mindfully and carefully and avoid any overlap.
Thank you sooo much!!! this was very informative!!!
|
|
Re: DOORS Question DXLUser - Wed Sep 14 17:55:11 EDT 2011 llandale - Sat Sep 10 20:00:49 EDT 2011
See "Recover" instead of "Cancel". Sorry, not so good at remembering those verbs.
To answer your original question, if you are done 'testing' you can "Return" the partition from the Away database and delete that Return file, and then "Recover" the partition in the Home, and you are back to the starting point. However, it seems to me you would want to practice "Return" at Away and then "Rejoin" at Home to complete your testing.
The Partition section in the DOORS User manual is actually pretty good and you should read it, play around a little, then read it again. Having a 2nd temp database will help a lot.
"Create Definition" is just playing around in the Home database getting read to make a partion. It defines which data goes and the access rights the Away folks will have.
"Remove Definition" is when the Home folks don't need that defintion anymore.
"Export Partition" is making a file for import into the Away database, and locks down any data in the Home that is editable in the Away.
"Import Partition" is loading the Partition in the Away database
"Synchronize" is when the Away folks have been editing but are not done, the Home folks can see the progress to date. Both the Away and the Home folks use the same verb; so lets pretend you "Synchronize Send" and "Synchronize Accept".
"Return" is when the Away folks are done editing and send the partition data back Home.
"Rejoin" is when the Home folks accept the Returned partition.
"Recover" is when the Home folks change their minds and don't want the Partition to come back. The Away folks should be advised so they can "Return" the partion, then delete the return files.
Now if you just want some Away folks to SEE your Home data but not edit any of it, you can create a read Definition, Export it, immediately Recover it, and the Away folks Import it. The Away folks could immediately Return it (with no home Rejoin), but they could also leave it as-is to remind them it's Home data.
Keeping in mind I've only played a little with partitions, I infer the following realities:
>> You cannot 'Remove' a Home definition while the Partion is Exported.
>> You cannot 'Remove' an Away Imported definition at all. This definition goes when you 'Return'.
>> If you were to Archive a project with an active Parition, I can see no way to coordinate such a Restored project with the Partition. That is, the restored project will not have that partition. Its thus possible that the DOORS folks deciced to disallow archiving of such Projects.
>> I imagine some difficulties if a module was in 2 partitions, even if its editable only in one.
>> I imagine some difficulties of putting a module you have Imported into an Exported Partion.
>> I imagine there are awkward scenarios the DOORS folks did not consider that will mess up your partitions very seriously.
You should architect your partitions mindfully and carefully and avoid any overlap.
What do I have to do if where Im submitting the partition to has a different version of DOORS?
|
|
Re: DOORS Question llandale - Thu Sep 15 12:59:38 EDT 2011 DXLUser - Wed Sep 14 17:55:11 EDT 2011
What do I have to do if where Im submitting the partition to has a different version of DOORS?
Since you cannot restore an Archive in a lesser major version (v8x) when archived in a greater version (v9x), I presume the same applies to Partitions. I imagine however you could send a read-only partition from lesser version to greater but perhaps they block that because they know you cannot send it back.
|
|
Re: DOORS Question DXLUser - Thu Sep 15 13:11:56 EDT 2011 llandale - Thu Sep 15 12:59:38 EDT 2011
Since you cannot restore an Archive in a lesser major version (v8x) when archived in a greater version (v9x), I presume the same applies to Partitions. I imagine however you could send a read-only partition from lesser version to greater but perhaps they block that because they know you cannot send it back.
Hi,
So if I have 8.3 and send a read only partition to someone who has 9.++ they will be able to import the partition without any problems?
|
|